home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
pcbt0990.zip
/
PCBTIC.DOC
< prev
next >
Wrap
Text File
|
1993-04-18
|
17KB
|
432 lines
PCBTIC ver 1.00 (c) Copyright XON/XOFF Computer Solutions, 1992
XON/XOFF Information Service
Robert & Joel Lechter
╒═════════════════════════════════════════════════════════════════════════╕
│ │
│ │
│ B E T A V E R S I O N │
│ │
│ │
╘═════════════════════════════════════════════════════════════════════════╛
■ Minimum Requirements:
· A 286 or better computer. 8086/8088 version is available upon
request.
· 220 KB conventional RAM.
· FrontDoor 2.02 & 2.10, BinkleyTerm, or D'Bridge 1.51. Other mailers
will be supported as time allows. Contact the author for specific
requests.
Due to the automatic mailer detection of PCBTIC, future mailer
versions may not function properly with PCBTIC. In that case,
contact the author of PCBTIC for an upgrade.
■ What is PCBTIC?
PCBTIC is the ultimate .TIC file processor for PCBoard.
PCBTIC is a program which will process incoming TIC files, and import
them into the PCBoard DIR Text File format (PCBoard file
descriptions).
Originally it was intended for our personal use in importing TIC
files to our PCBoard BBS. As our needs grew, so did the program.
When we were assigned FidoNet Hub status, we had to begin exporting
files, so the program was recoded. Then we had to start supporting
points, so more recoding. Little by little, the program has evolved
into the little monster that it is, with almost 6000 lines of code.
■ What is a TIC file?
A TIC file (named TKxxxxxx.TIC) is a file which accompanies
officially distributed File Distribution Network files. You probably
get a couple TIC's each week with your NODEDIFF and the Fido news
(FNEWSxxxx), but never really knew what to do with them. We USED to
delete them, but no more!
TIC files contain a bunch of information about the attached file,
including its path from the author to you, the description, and a
CRC.
■ Who needs it?
With the growing number of PCBoard BBS's which are becoming Fido
compatible (especially using FidoPCB), this is an essential program
to properly import incoming TIC files to the PCBoard DIR Text file
format. The original program, TICK, does not properly import the
descriptions into the PCBoard format--in spite of the documentation--
and, in fact, severely corrupts the descriptions, such that PCBFILER
can't access them.
I tried a number of other PCBoard TIC processors, and found their
abilities lacking; in previous versions of OTHER processors, files
were only able to be imported to one directory, or no real CRC
checking was done, or no redistribution of files was allowed.
■ Legal Stuff
We are currently running this program on our own multi-line PCBoard
(14.5a/10) BBS under LANtastic and it hasn't trashed anything, so I
guess it works. In fact, we are a FidoNet hub (look for us in the
NODELIST!), so we regularly redistribute files.
NOTE: PCBTIC does not yet support file/record locking. This will be
available in a future release.
■ How can you contact the author?
The easiest way you can send us a message, since you are a Fido
compatible system, is via NetMail to 1:167/159.
We can also be reached on our own 24 hour BBS at (514) 683-6729
(USRobotics Dual Standard 16800) or by fax at (514) 685-1152 (7am -
9pm Eastern Time).
Network addresses:
FidoNet: 1:167/159
KESHERnet: 18:716/201
FrancoMedia: 101:190/105
NAnet: 51/41/12
EchoNet: 51/40/52
Internet: Robert.Lechter@xonxoff.com
■ Why would you want to contact the author?
· First and foremost to report a bug.
· To send us your comments about the program.
· You might want to offer suggestions for added features in future
releases.
· To get information on custom versions.
I look forward to your input.
■ How do I set-up PCBTIC?
The configuration file is quite straightforward. There are two types
of area declarations.
Example #1:
AREA NODEDIFF <──── The area defined by the sender
c:\files\dirfl1 <──── where the descriptions go.
g:\pcb\fd\nodelist <──── where the file actually goes.
NODEDIFF <──── The password for this area
FROM 1:167/159 HISPASS <──── Straightforward, with password.
TO 1:1/1 PASS1 <──── Straightforward, with password.
TO 2:3/4.5 PASS2 NOTIC <──── As above, but no TIC file will
be made for this address.
TO 2:3/4 PASS NOTIC CRASH
TO 5:6/7 PASS HOLD
TO 1:2/2 PASS NOTIC HOLD
The above example indicates that the files will be imported into
PCBoard, as well as possibly being echoed, if there is a valid TO
directive.
Example #2:
AREA SOME_AREA
passthru
FROM ...
TO ...
The above example indicates that the files in this area will NOT be
imported into PCBoard, but merely echoed to the destination sites.
Please note that if no TO addresses are listed, any incoming files in
a PASSTHRU area will be deleted.
There are a few other switches in the CFG file that are user
adjustable.
REPLACE Optionally deletes old version of new files.
DUPECHECK Enables checking for duplicates based on CRC's.
CHANGEDATE Optionally changes the date of the incoming files, or
leave them as is. It is recommended that this switch
be left ON, since a (N)ew file scan will then work
properly.
CONFIG The directory for your mailer. PCBTIC will read that
configuration file for more information. This is to
make your life simpler by reducing the size and
complexity of this configuration file.
TIME Indicates how the program should handle the switch
from standard to daylight time. I have found the way
that other programs implement this (the TZ
environment variable) lacking, since it can't account
for variances between countries.
Format: TIME s, d, interval
where `s' indicates the number of hours to add to
current system time to get UTC (GMT) during
standard time (+5 for east coast of North
America)
`d' indicates the number of hours to add during
daylight savings time (+4 for east coast of
N.A.)
`interval' indicates the time interval that
savings time is in effect. It can be an
absolute date, such as `1 APR - 15 OCT' or a
relative date, such as `2 SUN APR - 5 TUE OCT'.
This relative date indicates the second Sunday
in April until the 5th (or last) Tuesday in
October.
If your system time is UTC, then you can simply use
TIME UTC (or TIME GMT).
■ Command line options:
/debug:n Logs more information for debugging purposes. Be
careful! The larger the number, the more info gets
placed into your log file.
WARNING: Level 9 makes HUGE log files, and has been
included for special debugging.
/nocrc Forces files with bad CRC's or TIC's with no CRC's to
be imported.
/hatch Sets PCBTIC into HATCH mode whereby it will originate
a file and send it out.
■ Is PCBTIC network aware?
Not yet. We are using it on a network, but haven't yet made it with
file locking and sharing capability. One catastrophe at a time,
please.
■ How do I hatch (originate) a file?
There are two ways to do this.
The first way, by simply typing "/hatch" on the command line, will run
PCBTIC's hatch option in interactive mode.
ex: PCBTIC /hatch
The second way is to use "/hatch=filespec" on the command line. Note,
that there are no spaces in this parameter. The filespec represents an
ASCII file which has the format which follows. This will allow you to
have automated hatchings, if you so desire.
line 1: Area name in which to hatch the file.
line 2: Full path and filename of the target file.
line 3: Description of the file.
line 4: OPTIONAL: The name of the file this file replaces.
ex: PCBTIC /hatch=f:\mydir\distrib1.dis
■ Why should I register PCBTIC?
If you find this program useful and time-saving, you should register
the program. This will ensure that we can properly support it.
Registration will also allow more than three areas to function.
Additionally, some companion programs will be released which will
work alongside PCBTIC. These programs will only work with the
registered version of PCBTIC.
■ How do I register PCBTIC?
Please see the PCBTIC.REG file (registartion form) and PCBTIC.VER
(version information) enclosed in this archive.
■ How much does registration cost?
A new fee structure has been announced.
The registration fee is 15$. This will enable all the features of
the program for 25 file areas (60 cents per area).
For more areas, please see the PCBTIC.VER file.
■ Three areas is not enough to properly evaluate PCBTIC.
We have now coded the program (starting at version 0.986) to accept a
DEMO key. This file can be obtained by sending NetMail to 1:167/159
with your mailer's address, and the number of conferences you wish to
evaluate.
A demo key file will be prepared, and you will be notified by return
NetMail that it is on hold for you.
■ Why is there no upper limit on the registration fee?
We have been asked this question quite a few times, and have pondered
whether or not to place a ceiling on the fees. Our conclusion was
not to limit the fee. After consulting with a number of SysOps, we
determined that 25 areas was reasonable. Once this number of file
areas is reached, that system is probably a commercial system.
Since PCBoard BBS's are often larger (i.e. more users, and more phone
lines) than other BBS programs, it is was not deemed fair to charge
an amateur system and a commercial system the same amount for the
program.
If you are an amateur system which does not charge its users, and
would really like to use PCBTIC, but the number of areas you carry
would price it out of your range, I suggest asking you users (or
those that download files) for a small (i.e. 2$) donation to pay for
this program and help offset your phone, and electric bills.
■ What does the REGISTERED version do that the unregistered doesn't?
Areas supported:
unr: a maximum of three areas.
reg: unlimited (actually limited by KEY file)
Nuisances:
unr: Delay upon program completion.
reg: No delay.
■ What will future 1.xx releases do?
· Well, network awareness is on the agenda, as well as support for
other front-end mailers.
· The .BAT file implementation is also scheduled for an overhaul.
· Detect of self-extracting archives.
· More mailer types will be supported.
■ What about future versions of PCBTIC?
No details are available yet, but some companion programs are in the
works.
■ Hints for proper integration of PCBTIC, your mailer, and your BBS.
Our mailer (FrontDoor) is set to exit after any file is received.
Here is the .BAT file segment that we use in order to integrate
PCBTIC into our BBS.
.
.
.
if not exist g:\frontdor\inbound\*.TIC goto NoTICK
usernet c:\pcb\main\usernet.xxx 1 Y * * "Processing new files"
f:
cd \pcbtic
rem * While the next two lines are not needed, we include them,
rem just in case the PCBTIC.EXE program is not found. It will
rem eliminate AFTER.BAT being run each time, and it will
rem eliminate the report file being inserted each time.
if exist after.bat del after.bat
if exist pcbtic.rpt del pcbtic.rpt
pcbtic
rem Update headers and check for viruses.
if exist after.bat call after
rem * Import new files report (This is all one command line.)
rem * Robert Vostrey's TXT2MSG program is required.
if exist pcbtic.rpt c:\txt2msg\txt2msg C:\PCB\MAIN\MSG -p -tALL
-fPCBTIC -sNEW_FILES_IN_CONF_2 pcbtic.rpt
rem Update PCBoard's download index files, if applicable.
call c:\pcb\refresh.bat
.
.
.
■ ERRORLEVELS
When PCBTIC exits, it will set the ERRORLEVEL which can be checked
by your .BAT file.
1 - Unable to open CFG file.
2 - Error message handler variable is out of bounds.
5 - Can't find inbound directory (as reported by mailer).
6 - Inbound directory is not a directory.
7 - Can't find outbound directory (as reported by mailer).
8 - Outbound directory is not a directory.
9 - Can't find MAIL directory (where MSG files go).
10 - MAIL directory is not a directory.
11 - Corrupt KEY file.
12 - Corrupt KEY file.
13 - Corrupt KEY file.
14 - Corrupt KEY file.
15 - KEY file is outdated.
16 - Unknown mailer type.
17 - Can't find mailer's directory.
18 - mailer's directory is not a directory.
20 - Can't find mailer's directory.
21 - Error in SETUP.FD file (FrontDoor only).
22 - No CONFIG entry in PCBTIC.CFG.
30 - Can't create work directory.
31 - Can't create work directory.
32 - Error in TIME directive
33 - No INBOUND directories in configuration file.
34 - Error in your address (in mailer configuration)
■ Echoing files
PCBTIC can redistribute files to other sites. This allows PCBoard
BBS's to act as Fido hubs (as we are), or even as File Distibution
Network Systems.
■ Revision History
Please see the PCBTIC.HST file.
■ Final Notes
You are encouraged to send this file to other SysOps operating
PCBoard and front-end mailers. If you do, please include the entire
archive in its original format, and do not change the distribution
name from the original name.
We are interested in as much feedback as possible, so please drop us
a line.
We freqent the FidoNet PCBNET conference, the FidoPCB support
conference, and the PCBoard Support conference. Of course, NetMail
is always welcome!
Robert & Joel Lechter
FidoNet 1:167/159